Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 921c9004e6fc5ef03a6995e9b7f657a5e4df7517e0413b8a242274ba46aa012a

Tx prefix hash: 8462eeb01a838b3083a7be4446ad4caf47f41b7830340dac8d7240a983fda535
Tx public key: 6e360c5456b027f96bc44d36a4f2fe4823806fe0eed6cb690bf0bf1f3bd26603
Timestamp: 1715936778 Timestamp [UCT]: 2024-05-17 09:06:18 Age [y:d:h:m:s]: 00:328:13:36:55
Block: 1023878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234840 RingCT/type: yes/0
Extra: 016e360c5456b027f96bc44d36a4f2fe4823806fe0eed6cb690bf0bf1f3bd2660302110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42a99ede7369d191b444641a151fdbf54694cf4dc6ca26d8d8f450a38834a580 0.600000000000 1489181 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": 1023888, "vin": [ { "gen": { "height": 1023878 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42a99ede7369d191b444641a151fdbf54694cf4dc6ca26d8d8f450a38834a580" } } ], "extra": [ 1, 110, 54, 12, 84, 86, 176, 39, 249, 107, 196, 77, 54, 164, 242, 254, 72, 35, 128, 111, 224, 238, 214, 203, 105, 11, 240, 191, 31, 59, 210, 102, 3, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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