Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd09871dba9d3340eb7d764478cf9d1c6834e8148bcd043c201cf6ebf83fa343

Tx prefix hash: b5f22ca30f083c43d9d037d114e8f3f519a55e65d093671928f51c0796db8b2f
Tx public key: b01ab39919443f7bfc50e93a0bc7292d026a4cb4bf8ab2cc9831b3c8bfe8a4f0
Timestamp: 1706620704 Timestamp [UCT]: 2024-01-30 13:18:24 Age [y:d:h:m:s]: 01:065:16:27:14
Block: 946613 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308024 RingCT/type: yes/0
Extra: 01b01ab39919443f7bfc50e93a0bc7292d026a4cb4bf8ab2cc9831b3c8bfe8a4f002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 029d5a56332e5068c6d503c102aea0b215a0de44387c2a15b582fe57dbcdb972 0.600000000000 1404947 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": 946623, "vin": [ { "gen": { "height": 946613 } } ], "vout": [ { "amount": 600000000, "target": { "key": "029d5a56332e5068c6d503c102aea0b215a0de44387c2a15b582fe57dbcdb972" } } ], "extra": [ 1, 176, 26, 179, 153, 25, 68, 63, 123, 252, 80, 233, 58, 11, 199, 41, 45, 2, 106, 76, 180, 191, 138, 178, 204, 152, 49, 179, 200, 191, 232, 164, 240, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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