Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c9479fe3171cd8fa7a2d870fd7433951bb890d57316920da4d29a4511c57a70

Tx prefix hash: 29f8608efdb5e2af1bcb7ae252864d15a783d9690dacae21584c6af5dbd6bf38
Tx public key: 2206eb47d1e181f9c4e61319edf0da580d7a017eb223e47b831a7e39f19e5998
Timestamp: 1577958168 Timestamp [UCT]: 2020-01-02 09:42:48 Age [y:d:h:m:s]: 05:165:00:27:23
Block: 37102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1267669 RingCT/type: yes/0
Extra: 012206eb47d1e181f9c4e61319edf0da580d7a017eb223e47b831a7e39f19e59980211000000084943cd9f000000000000000000

1 output(s) for total of 462.451853154000 dcy

stealth address amount amount idx
00: cf00835645bbcaa2dff412b9205ce004ca8a908a4a8f7492c24f73e9b2f890b7 462.451853154000 62924 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": 37112, "vin": [ { "gen": { "height": 37102 } } ], "vout": [ { "amount": 462451853154, "target": { "key": "cf00835645bbcaa2dff412b9205ce004ca8a908a4a8f7492c24f73e9b2f890b7" } } ], "extra": [ 1, 34, 6, 235, 71, 209, 225, 129, 249, 196, 230, 19, 25, 237, 240, 218, 88, 13, 122, 1, 126, 178, 35, 228, 123, 131, 26, 126, 57, 241, 158, 89, 152, 2, 17, 0, 0, 0, 8, 73, 67, 205, 159, 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