Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ecfae121a2e8aabc6f8b8729c4208d35db649610ff4f3a5287595afeb7530f32

Tx prefix hash: 1a648642c999ad63977efa566f24f927be92156368f4763b069c2868ec70e591
Tx public key: 3a64f220770cd6e59b769d31723d93d8a0b1726e0e3e496ca1bbf75503d4f8f5
Timestamp: 1724966498 Timestamp [UCT]: 2024-08-29 21:21:38 Age [y:d:h:m:s]: 00:132:07:51:48
Block: 1098726 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94654 RingCT/type: yes/0
Extra: 013a64f220770cd6e59b769d31723d93d8a0b1726e0e3e496ca1bbf75503d4f8f5021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66eac16335207f7927395628ee34e4e9347cc818d2807d7600a2a9cc873f2e4d 0.600000000000 1574541 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": 1098736, "vin": [ { "gen": { "height": 1098726 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66eac16335207f7927395628ee34e4e9347cc818d2807d7600a2a9cc873f2e4d" } } ], "extra": [ 1, 58, 100, 242, 32, 119, 12, 214, 229, 155, 118, 157, 49, 114, 61, 147, 216, 160, 177, 114, 110, 14, 62, 73, 108, 161, 187, 247, 85, 3, 212, 248, 245, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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