Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad004729c587f47b152c5789ca34d19d6d344da87795ea4381277cbcdb67bc27

Tx prefix hash: 349a37d4cd48ba882868f9aa525223399539c05ab5a6a1f747fc84b2ebb5d05b
Tx public key: 1d6e16923705ccebb3d5c6fc8e6b3343ad0a5083df439e1feb139ecfe8d1ae23
Timestamp: 1735411444 Timestamp [UCT]: 2024-12-28 18:44:04 Age [y:d:h:m:s]: 00:171:22:23:38
Block: 1185187 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122605 RingCT/type: yes/0
Extra: 011d6e16923705ccebb3d5c6fc8e6b3343ad0a5083df439e1feb139ecfe8d1ae230211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d75dd658165cdc5bbc03669c6efa4d1e11b568227d4c172e5f835f0d6f5e9e0a 0.600000000000 1671654 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": 1185197, "vin": [ { "gen": { "height": 1185187 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d75dd658165cdc5bbc03669c6efa4d1e11b568227d4c172e5f835f0d6f5e9e0a" } } ], "extra": [ 1, 29, 110, 22, 146, 55, 5, 204, 235, 179, 213, 198, 252, 142, 107, 51, 67, 173, 10, 80, 131, 223, 67, 158, 31, 235, 19, 158, 207, 232, 209, 174, 35, 2, 17, 0, 0, 0, 2, 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