Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5255f1b461e068e24e50e4eb0077e928d2f57df9d5e7ee84c76d11081ba90d19

Tx prefix hash: 7f95de58e2372a13c7c597dd772b68969b0a31d0e652c0bdfbe4d5e772410c5e
Tx public key: 0aeb3b07fb1a08014e0a36134e52e4e1b3b0aa3112e3339f29226f4d9680dafd
Timestamp: 1727769532 Timestamp [UCT]: 2024-10-01 07:58:52 Age [y:d:h:m:s]: 01:041:11:39:23
Block: 1121972 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288040 RingCT/type: yes/0
Extra: 010aeb3b07fb1a08014e0a36134e52e4e1b3b0aa3112e3339f29226f4d9680dafd021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40af0092c54e22b163287aaf47c3833789a96b488f4676745214f4e209622a33 0.600000000000 1604337 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": 1121982, "vin": [ { "gen": { "height": 1121972 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40af0092c54e22b163287aaf47c3833789a96b488f4676745214f4e209622a33" } } ], "extra": [ 1, 10, 235, 59, 7, 251, 26, 8, 1, 78, 10, 54, 19, 78, 82, 228, 225, 179, 176, 170, 49, 18, 227, 51, 159, 41, 34, 111, 77, 150, 128, 218, 253, 2, 17, 0, 0, 0, 8, 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