Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cecdb97d638905ed30a180102ce768718d6563a0c56e67a209df5050555c1901

Tx prefix hash: b2d8a9d70663b4aeb9a93a4a7b3d3d6a7f225f759d4428a197e8282a91bd249f
Tx public key: ccb715df4881e385d891154b2021d14b413df5d2e2bbf62fd4fa6034535d8b95
Timestamp: 1735588409 Timestamp [UCT]: 2024-12-30 19:53:29 Age [y:d:h:m:s]: 00:170:04:47:07
Block: 1186657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121351 RingCT/type: yes/0
Extra: 01ccb715df4881e385d891154b2021d14b413df5d2e2bbf62fd4fa6034535d8b95021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c95930a5eece4a2baf459b8b4e9acf2fc5eae9302fa2768d468dcc3c6052bf7e 0.600000000000 1673140 of 15

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": 1186667, "vin": [ { "gen": { "height": 1186657 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c95930a5eece4a2baf459b8b4e9acf2fc5eae9302fa2768d468dcc3c6052bf7e" } } ], "extra": [ 1, 204, 183, 21, 223, 72, 129, 227, 133, 216, 145, 21, 75, 32, 33, 209, 75, 65, 61, 245, 210, 226, 187, 246, 47, 212, 250, 96, 52, 83, 93, 139, 149, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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