Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 50637e79d05a131d987044ee8ee90b1331ce561d89800b3f0d5f495778184263

Tx prefix hash: 61e73c47e64e1f4040b42fc784780d9c1790f5980fbcb9e9d3e6f82927102c93
Tx public key: f6937633098f4c5a243bcf6a4eb5ab7a23dee5353edbc84401c222939c001722
Timestamp: 1697127185 Timestamp [UCT]: 2023-10-12 16:13:05 Age [y:d:h:m:s]: 01:034:21:34:35
Block: 868146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286134 RingCT/type: yes/0
Extra: 01f6937633098f4c5a243bcf6a4eb5ab7a23dee5353edbc84401c222939c00172202110000000a4b8f5122000000000000000000

1 output(s) for total of 0.815590104000 dcy

stealth address amount amount idx
00: 31f52d930c2cfa9718c77e7ae01c68c2c2e56deae7a1a6d11ff6e13ffe12d93e 0.815590104000 1322917 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 868156, "vin": [ { "gen": { "height": 868146 } } ], "vout": [ { "amount": 815590104, "target": { "key": "31f52d930c2cfa9718c77e7ae01c68c2c2e56deae7a1a6d11ff6e13ffe12d93e" } } ], "extra": [ 1, 246, 147, 118, 51, 9, 143, 76, 90, 36, 59, 207, 106, 78, 181, 171, 122, 35, 222, 229, 53, 62, 219, 200, 68, 1, 194, 34, 147, 156, 0, 23, 34, 2, 17, 0, 0, 0, 10, 75, 143, 81, 34, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8