Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f88be5bfcd5b15aa413811aecb6644444ef4272e15f4090eee7a7aff4fee18d2

Tx prefix hash: d4a9df46999ce4a0569324afebba5c91d7b5b36a5e985788cf5516399b2abea0
Tx public key: 75128fc6e2d7467c7bdee545ff502e144119ec59c2f6986f546e492d2da2336b
Timestamp: 1704736329 Timestamp [UCT]: 2024-01-08 17:52:09 Age [y:d:h:m:s]: 01:109:17:38:25
Block: 931001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339553 RingCT/type: yes/0
Extra: 0175128fc6e2d7467c7bdee545ff502e144119ec59c2f6986f546e492d2da2336b02110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 190dcd1b5ea4d3f3edc416418ba888b78ccf0d273930d2d9ac14713b81e191e1 0.600000000000 1388893 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": 931011, "vin": [ { "gen": { "height": 931001 } } ], "vout": [ { "amount": 600000000, "target": { "key": "190dcd1b5ea4d3f3edc416418ba888b78ccf0d273930d2d9ac14713b81e191e1" } } ], "extra": [ 1, 117, 18, 143, 198, 226, 215, 70, 124, 123, 222, 229, 69, 255, 80, 46, 20, 65, 25, 236, 89, 194, 246, 152, 111, 84, 110, 73, 45, 45, 162, 51, 107, 2, 17, 0, 0, 0, 10, 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