Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86ce158f169f7bd572863f2c2dbead0c89aca3e8f19e9444a28dcdb87ebb84b5

Tx prefix hash: d6fa791ff750c944d3aafaba6ba83e035e6d4eaffc50ad8072066cdfe6379a6e
Tx public key: 656be9ef03150ddbb0c32dc7bd7b4e25bb273e2caf4e416e9efd4134372c7ff5
Timestamp: 1736338680 Timestamp [UCT]: 2025-01-08 12:18:00 Age [y:d:h:m:s]: 00:301:13:32:53
Block: 1192871 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213010 RingCT/type: yes/0
Extra: 01656be9ef03150ddbb0c32dc7bd7b4e25bb273e2caf4e416e9efd4134372c7ff50211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc6eb219fa0f0f1b42cb466cdda5523c706c351e57cf0a51f475d92990d3daf2 0.600000000000 1679428 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": 1192881, "vin": [ { "gen": { "height": 1192871 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc6eb219fa0f0f1b42cb466cdda5523c706c351e57cf0a51f475d92990d3daf2" } } ], "extra": [ 1, 101, 107, 233, 239, 3, 21, 13, 219, 176, 195, 45, 199, 189, 123, 78, 37, 187, 39, 62, 44, 175, 78, 65, 110, 158, 253, 65, 52, 55, 44, 127, 245, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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