Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 178bca02137222c59fc1f8b0e432dac3a2421b170433910406e0ce05d9c686dc

Tx prefix hash: c990b00239fa2c9feab2df75f16fb0926caa55583ad29d64ee45acc53499f7b6
Tx public key: f6cf927a22c6b088c91bad31b7eda03f680c9fcc2213f243510f376770ad6c32
Timestamp: 1736060771 Timestamp [UCT]: 2025-01-05 07:06:11 Age [y:d:h:m:s]: 00:164:05:25:43
Block: 1190581 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117076 RingCT/type: yes/0
Extra: 01f6cf927a22c6b088c91bad31b7eda03f680c9fcc2213f243510f376770ad6c32021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84f74c04b035c8e8a066e5c4cb3db56eb4246a6c74523a3e8130d43d312b0c0f 0.600000000000 1677098 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": 1190591, "vin": [ { "gen": { "height": 1190581 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84f74c04b035c8e8a066e5c4cb3db56eb4246a6c74523a3e8130d43d312b0c0f" } } ], "extra": [ 1, 246, 207, 146, 122, 34, 198, 176, 136, 201, 27, 173, 49, 183, 237, 160, 63, 104, 12, 159, 204, 34, 19, 242, 67, 81, 15, 55, 103, 112, 173, 108, 50, 2, 17, 0, 0, 0, 2, 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