Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ec8b9a91aea15c413ce33e62715607d847af3c710cc754b1312ed9149c511c6

Tx prefix hash: 87d81190d16a0228220af69a3adfe90be1e98cb84ddb2a78abae18e14f2be447
Tx public key: 4876f8565868ef8d9c868036a58a6e4eea8668b378f1fdcd90e48bd5d799f3bf
Timestamp: 1710531141 Timestamp [UCT]: 2024-03-15 19:32:21 Age [y:d:h:m:s]: 01:022:09:04:36
Block: 979070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276952 RingCT/type: yes/0
Extra: 014876f8565868ef8d9c868036a58a6e4eea8668b378f1fdcd90e48bd5d799f3bf02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4f33d272f08a59cbf0252f434f97e1887054d82493a2954d4a1e24b4e9799b5 0.600000000000 1439101 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": 979080, "vin": [ { "gen": { "height": 979070 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4f33d272f08a59cbf0252f434f97e1887054d82493a2954d4a1e24b4e9799b5" } } ], "extra": [ 1, 72, 118, 248, 86, 88, 104, 239, 141, 156, 134, 128, 54, 165, 138, 110, 78, 234, 134, 104, 179, 120, 241, 253, 205, 144, 228, 139, 213, 215, 153, 243, 191, 2, 17, 0, 0, 0, 3, 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