Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30f17a2c5c5331b7302fc61ef73f81993311fca40c77211d740c80ec8ded6239

Tx prefix hash: 56b9e04f02ec162b5f9ad37db836ddff0633951dcadccfeb6e6be9965c103f1c
Tx public key: cbb595871f9764e3515f44b20281af41e283cba04154b05b8f6b26cb67d2df18
Timestamp: 1584924503 Timestamp [UCT]: 2020-03-23 00:48:23 Age [y:d:h:m:s]: 05:227:03:49:20
Block: 87076 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1317477 RingCT/type: yes/0
Extra: 01cbb595871f9764e3515f44b20281af41e283cba04154b05b8f6b26cb67d2df1802110000007cc2c2f844000000000000000000

1 output(s) for total of 315.850700641000 dcy

stealth address amount amount idx
00: b52d5b86c6186f61ad4c05e92f23a4053d60e7cd0a5c7d3b91d94e15a3326434 315.850700641000 156986 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": 87086, "vin": [ { "gen": { "height": 87076 } } ], "vout": [ { "amount": 315850700641, "target": { "key": "b52d5b86c6186f61ad4c05e92f23a4053d60e7cd0a5c7d3b91d94e15a3326434" } } ], "extra": [ 1, 203, 181, 149, 135, 31, 151, 100, 227, 81, 95, 68, 178, 2, 129, 175, 65, 226, 131, 203, 160, 65, 84, 176, 91, 143, 107, 38, 203, 103, 210, 223, 24, 2, 17, 0, 0, 0, 124, 194, 194, 248, 68, 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