Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b1d1594730f4eec52c4cba4b9c8918cc5314c04d18c29fd724042e2f90b4fdb

Tx prefix hash: 5a2f9f025bf2756cc053b0992a3adbbd905b17177a6b9a4042f84dd9f3ea6fc7
Tx public key: 547b34a072738ab01f3320d0fb5417e89f658fdcb147f563d767ce430ab86da9
Timestamp: 1713012215 Timestamp [UCT]: 2024-04-13 12:43:35 Age [y:d:h:m:s]: 00:364:20:42:16
Block: 999607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260864 RingCT/type: yes/0
Extra: 01547b34a072738ab01f3320d0fb5417e89f658fdcb147f563d767ce430ab86da90211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 273ed331a2b69f142cd5f9e104f03378516acc96467fd52e916f1d78e9016501 0.600000000000 1460089 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": 999617, "vin": [ { "gen": { "height": 999607 } } ], "vout": [ { "amount": 600000000, "target": { "key": "273ed331a2b69f142cd5f9e104f03378516acc96467fd52e916f1d78e9016501" } } ], "extra": [ 1, 84, 123, 52, 160, 114, 115, 138, 176, 31, 51, 32, 208, 251, 84, 23, 232, 159, 101, 143, 220, 177, 71, 245, 99, 215, 103, 206, 67, 10, 184, 109, 169, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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