Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cbf7a6881192347f7691a30528e59b7083fb064a1a6920bb8adbaf9ebd36015

Tx prefix hash: bc71d8998a0ec86e69855fa5c106617e68d058d5dd978b4e898972484889e3de
Tx public key: dd8d4b510cfc1ee9201cc340ef04581c041311de470fb49a302aa6e33dcbd378
Timestamp: 1612740081 Timestamp [UCT]: 2021-02-07 23:21:21 Age [y:d:h:m:s]: 04:266:17:45:33
Block: 194142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1207924 RingCT/type: yes/0
Extra: 01dd8d4b510cfc1ee9201cc340ef04581c041311de470fb49a302aa6e33dcbd37802110000041bc6b81c9d000000000000000000

1 output(s) for total of 139.551687810000 dcy

stealth address amount amount idx
00: 4b4f777fdecf79fb5a19c1f5841971e3a658dabc7454330179215791baa26bf5 139.551687810000 393696 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": 194152, "vin": [ { "gen": { "height": 194142 } } ], "vout": [ { "amount": 139551687810, "target": { "key": "4b4f777fdecf79fb5a19c1f5841971e3a658dabc7454330179215791baa26bf5" } } ], "extra": [ 1, 221, 141, 75, 81, 12, 252, 30, 233, 32, 28, 195, 64, 239, 4, 88, 28, 4, 19, 17, 222, 71, 15, 180, 154, 48, 42, 166, 227, 61, 203, 211, 120, 2, 17, 0, 0, 4, 27, 198, 184, 28, 157, 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