Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 583e3aaee25385138e41b7a8eae29071fb69715a66bbe579ae0b840eabe23afc

Tx prefix hash: 3ef9ef8117a9e9a92e48dce7056702c187ec140408a9252bbd9ca18199c73827
Tx public key: 0b8f3af417f89f67923b63c0cd0f10c2d1af4b7e1d7c2cd05a2dcfcf895edda7
Timestamp: 1734032865 Timestamp [UCT]: 2024-12-12 19:47:45 Age [y:d:h:m:s]: 00:106:10:19:12
Block: 1173808 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75835 RingCT/type: yes/0
Extra: 010b8f3af417f89f67923b63c0cd0f10c2d1af4b7e1d7c2cd05a2dcfcf895edda70211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 22e280e2aba9856694fac3d52829ec4c4a4edeba653c699f87d43e42b7988082 0.600000000000 1659875 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": 1173818, "vin": [ { "gen": { "height": 1173808 } } ], "vout": [ { "amount": 600000000, "target": { "key": "22e280e2aba9856694fac3d52829ec4c4a4edeba653c699f87d43e42b7988082" } } ], "extra": [ 1, 11, 143, 58, 244, 23, 248, 159, 103, 146, 59, 99, 192, 205, 15, 16, 194, 209, 175, 75, 126, 29, 124, 44, 208, 90, 45, 207, 207, 137, 94, 221, 167, 2, 17, 0, 0, 0, 5, 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