Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1726e640f9f1bb3d9941a4f156fd87428fd6a2c4f2ba0c05356206e72b486e0

Tx prefix hash: cd2821bd888a9b7f3aefbdbb637ce6c345485b3256ef6cc15cdd87d0599e5841
Tx public key: f7c532bf1e41e8f108f4d7e556373d0976929d59b0b0250f00e0aca68f4ac2e9
Timestamp: 1704000254 Timestamp [UCT]: 2023-12-31 05:24:14 Age [y:d:h:m:s]: 01:060:09:58:25
Block: 924898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304272 RingCT/type: yes/0
Extra: 01f7c532bf1e41e8f108f4d7e556373d0976929d59b0b0250f00e0aca68f4ac2e90211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e902794c6a1cd5650c775a4b1a9b95b025e07d9b8cc15372ac9c6dfab5882a0 0.600000000000 1382658 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": 924908, "vin": [ { "gen": { "height": 924898 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e902794c6a1cd5650c775a4b1a9b95b025e07d9b8cc15372ac9c6dfab5882a0" } } ], "extra": [ 1, 247, 197, 50, 191, 30, 65, 232, 241, 8, 244, 215, 229, 86, 55, 61, 9, 118, 146, 157, 89, 176, 176, 37, 15, 0, 224, 172, 166, 143, 74, 194, 233, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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