Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76f1c2978132788b0dabc5a633857df7a035f33dcae1a3071cb85612f6c56126

Tx prefix hash: 7efe90e1856affee78da78f5893de378c0e6526d58b55efce496946730be337d
Tx public key: 22983df39e078bf3f80556a634011b34cf04d9b35fcd10f9259e4e1ca3b333e9
Timestamp: 1727412473 Timestamp [UCT]: 2024-09-27 04:47:53 Age [y:d:h:m:s]: 00:169:10:09:41
Block: 1119015 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120902 RingCT/type: yes/0
Extra: 0122983df39e078bf3f80556a634011b34cf04d9b35fcd10f9259e4e1ca3b333e9021100000009e914dd15000000000000000000

1 output(s) for total of 0.608010000000 dcy

stealth address amount amount idx
00: 369c2acb4efa0ec810393b3bffb5fd85b3eaede2ca48bd43765c0d3fe65c3b16 0.608010000000 1600408 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": 1119025, "vin": [ { "gen": { "height": 1119015 } } ], "vout": [ { "amount": 608010000, "target": { "key": "369c2acb4efa0ec810393b3bffb5fd85b3eaede2ca48bd43765c0d3fe65c3b16" } } ], "extra": [ 1, 34, 152, 61, 243, 158, 7, 139, 243, 248, 5, 86, 166, 52, 1, 27, 52, 207, 4, 217, 179, 95, 205, 16, 249, 37, 158, 78, 28, 163, 179, 51, 233, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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