Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 796ce225ed6d55c2245d0c578d924628da39e36104e03133acdf3296b77395ae

Tx prefix hash: 44541bfd3e83d979d7d52841ca8d5601080d66995f4f40ec2ce3af779010a2df
Tx public key: 244bc1834047c1f36d70f7626d1484e70c8a3b1d0a620dbf0c9ba41180771077
Timestamp: 1581092086 Timestamp [UCT]: 2020-02-07 16:14:46 Age [y:d:h:m:s]: 05:026:04:01:16
Block: 60736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1170732 RingCT/type: yes/0
Extra: 01244bc1834047c1f36d70f7626d1484e70c8a3b1d0a620dbf0c9ba411807710770211000000334ac5aa02000000000000000000

1 output(s) for total of 386.174984631000 dcy

stealth address amount amount idx
00: c1dface3020f862acfe129c126b6e6b5b10317fe5d9a0d238326643d0da266c4 386.174984631000 111805 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": 60746, "vin": [ { "gen": { "height": 60736 } } ], "vout": [ { "amount": 386174984631, "target": { "key": "c1dface3020f862acfe129c126b6e6b5b10317fe5d9a0d238326643d0da266c4" } } ], "extra": [ 1, 36, 75, 193, 131, 64, 71, 193, 243, 109, 112, 247, 98, 109, 20, 132, 231, 12, 138, 59, 29, 10, 98, 13, 191, 12, 155, 164, 17, 128, 119, 16, 119, 2, 17, 0, 0, 0, 51, 74, 197, 170, 2, 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