Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8b54cefd3990a242ff627166787d9aae88ad3ef74c4de87dfd1361c815f2078

Tx prefix hash: a6c286119d4e2cf44c18df1cf7bcff598ed787e3e6d43716da237bb2ea292ef3
Tx public key: 26f3d08965671d13a27f1acccede21bec54bb5718bf7730a8f5df6bfc398af43
Timestamp: 1748248517 Timestamp [UCT]: 2025-05-26 08:35:17 Age [y:d:h:m:s]: 00:193:00:52:54
Block: 1291219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135681 RingCT/type: yes/0
Extra: 0126f3d08965671d13a27f1acccede21bec54bb5718bf7730a8f5df6bfc398af430211000000031f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc1b9b1632a1a1b369c4c163e17ae8c3987e6097ead6187bb2c3c4a1727eeec0 0.600000000000 1778690 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": 1291229, "vin": [ { "gen": { "height": 1291219 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc1b9b1632a1a1b369c4c163e17ae8c3987e6097ead6187bb2c3c4a1727eeec0" } } ], "extra": [ 1, 38, 243, 208, 137, 101, 103, 29, 19, 162, 127, 26, 204, 206, 222, 33, 190, 197, 75, 181, 113, 139, 247, 115, 10, 143, 93, 246, 191, 195, 152, 175, 67, 2, 17, 0, 0, 0, 3, 31, 144, 81, 122, 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