Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98a46cde91f2401dc56a29b1c9209af6bd9b5dc2e21945725bf3fec173e4ea5d

Tx prefix hash: 779ec39711d732117a44885c91be576f3d6298ce8ee4c891c4bad10862b4333e
Tx public key: 50f9bee1e80a3fd11978e55c62064f22ab7f547f95c32f2db9488055b868dd0b
Timestamp: 1661752356 Timestamp [UCT]: 2022-08-29 05:52:36 Age [y:d:h:m:s]: 02:120:11:43:07
Block: 576164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 607566 RingCT/type: yes/0
Extra: 0150f9bee1e80a3fd11978e55c62064f22ab7f547f95c32f2db9488055b868dd0b021100000012e6d27f9c000000000000000000

1 output(s) for total of 7.567101945000 dcy

stealth address amount amount idx
00: e5213c09dfe9b100baa8983077e86432cb67dd7c99c32eb116c86d02a3f06a29 7.567101945000 1009508 of 0

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": 576174, "vin": [ { "gen": { "height": 576164 } } ], "vout": [ { "amount": 7567101945, "target": { "key": "e5213c09dfe9b100baa8983077e86432cb67dd7c99c32eb116c86d02a3f06a29" } } ], "extra": [ 1, 80, 249, 190, 225, 232, 10, 63, 209, 25, 120, 229, 92, 98, 6, 79, 34, 171, 127, 84, 127, 149, 195, 47, 45, 185, 72, 128, 85, 184, 104, 221, 11, 2, 17, 0, 0, 0, 18, 230, 210, 127, 156, 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