Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6cca8248298b3efc81498ce5681f37a139812dfc92de325a0dd6f6c12279d71b

Tx prefix hash: 76f5cb71f4f3b32722442bdf5c9956f9a95be18c12b779cc3756a20d5e0407a3
Tx public key: dd710f7ff852d7009ad38da60fff6ef7a2fbd94320811c654e9c14176d2f5883
Timestamp: 1728836255 Timestamp [UCT]: 2024-10-13 16:17:35 Age [y:d:h:m:s]: 00:248:20:04:57
Block: 1130812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177530 RingCT/type: yes/0
Extra: 01dd710f7ff852d7009ad38da60fff6ef7a2fbd94320811c654e9c14176d2f588302110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8e45fa5e398f8f02bd54f242037ed0ae44eb4a084f8787c4b7a94247d43d8f1 0.600000000000 1613693 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": 1130822, "vin": [ { "gen": { "height": 1130812 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8e45fa5e398f8f02bd54f242037ed0ae44eb4a084f8787c4b7a94247d43d8f1" } } ], "extra": [ 1, 221, 113, 15, 127, 248, 82, 215, 0, 154, 211, 141, 166, 15, 255, 110, 247, 162, 251, 217, 67, 32, 129, 28, 101, 78, 156, 20, 23, 109, 47, 88, 131, 2, 17, 0, 0, 0, 12, 145, 225, 60, 4, 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