Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81e8ec44d1894a07fe4ac8d5f41b500e1f6113d71f490f6798fdd7c61b47964e

Tx prefix hash: 6912d1195b4911722556ff4bc1622cba21e99b1aff3be622a7ecca72308d97a5
Tx public key: b777f552799fde73e1b03f20cbbff89881a40c3a0a9d8ac1de39e7ff5b3430f3
Timestamp: 1719546802 Timestamp [UCT]: 2024-06-28 03:53:22 Age [y:d:h:m:s]: 01:134:06:38:20
Block: 1053801 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354502 RingCT/type: yes/0
Extra: 01b777f552799fde73e1b03f20cbbff89881a40c3a0a9d8ac1de39e7ff5b3430f30211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69beb42d44921e2e566166182877e6b3e132514b5aa182842761ae143b0b1370 0.600000000000 1524152 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": 1053811, "vin": [ { "gen": { "height": 1053801 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69beb42d44921e2e566166182877e6b3e132514b5aa182842761ae143b0b1370" } } ], "extra": [ 1, 183, 119, 245, 82, 121, 159, 222, 115, 225, 176, 63, 32, 203, 191, 248, 152, 129, 164, 12, 58, 10, 157, 138, 193, 222, 57, 231, 255, 91, 52, 48, 243, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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