Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b72c63cc5222e0115b60491223d18eb452e8f5edd985f722e5859664ba24ffce

Tx prefix hash: 676e1a69b6f368f85d73405fb13ca99c0a5f0da72d670a795bd3cb0b714e92a5
Tx public key: 6f0910d3e73f6cfe39f4088fd74cf0003ac4aa3dbdaeab683733bd5a8fa2df2b
Timestamp: 1578821087 Timestamp [UCT]: 2020-01-12 09:24:47 Age [y:d:h:m:s]: 05:022:19:30:41
Block: 43823 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1166438 RingCT/type: yes/0
Extra: 016f0910d3e73f6cfe39f4088fd74cf0003ac4aa3dbdaeab683733bd5a8fa2df2b02110000005c391a8d0e000000000000000000

1 output(s) for total of 439.336262641000 dcy

stealth address amount amount idx
00: e48ba674855626f85920e069dab6df41512e4057654f70e29db5ed82e0b901d1 439.336262641000 79510 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": 43833, "vin": [ { "gen": { "height": 43823 } } ], "vout": [ { "amount": 439336262641, "target": { "key": "e48ba674855626f85920e069dab6df41512e4057654f70e29db5ed82e0b901d1" } } ], "extra": [ 1, 111, 9, 16, 211, 231, 63, 108, 254, 57, 244, 8, 143, 215, 76, 240, 0, 58, 196, 170, 61, 189, 174, 171, 104, 55, 51, 189, 90, 143, 162, 223, 43, 2, 17, 0, 0, 0, 92, 57, 26, 141, 14, 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