Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ad41f1d63c93107bbcec3a072e2d282000072ccd04630fbb0b43adb0de96eeb

Tx prefix hash: 00b6da06a5d6c3b815b614cc0e5a4ddc9d944bc39f2baa0fed6e72eb227c84c9
Tx public key: b9de8b3224ff814108f55942bc709d82046dc97783f359fa2d27901b58a17ea7
Timestamp: 1716595583 Timestamp [UCT]: 2024-05-25 00:06:23 Age [y:d:h:m:s]: 01:166:18:45:56
Block: 1029341 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377779 RingCT/type: yes/0
Extra: 01b9de8b3224ff814108f55942bc709d82046dc97783f359fa2d27901b58a17ea702110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b058c6573ea4d0afe55bd65adec56d784355eb1f6248987f6e0a4551b1a6d67 0.600000000000 1497404 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": 1029351, "vin": [ { "gen": { "height": 1029341 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b058c6573ea4d0afe55bd65adec56d784355eb1f6248987f6e0a4551b1a6d67" } } ], "extra": [ 1, 185, 222, 139, 50, 36, 255, 129, 65, 8, 245, 89, 66, 188, 112, 157, 130, 4, 109, 201, 119, 131, 243, 89, 250, 45, 39, 144, 27, 88, 161, 126, 167, 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