Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28443b2a8f4e9d034476cb1ae06216a94a45fc20ce9eb80edec9bc60b3fad555

Tx prefix hash: 7e2b9cb3afe663a77328d526074b118948cfc87dca526fc237fcb41437205f10
Tx public key: 8f75e2b7a4f8b3b64e0edd6e33805d94fcc90c1b15c631a9a8390aa9cff86584
Timestamp: 1731456613 Timestamp [UCT]: 2024-11-13 00:10:13 Age [y:d:h:m:s]: 00:010:22:09:45
Block: 1152434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7824 RingCT/type: yes/0
Extra: 018f75e2b7a4f8b3b64e0edd6e33805d94fcc90c1b15c631a9a8390aa9cff865840211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56b4616938b29f9500ed2ba97add896e1a09f9bef3790f391dcb5b7bd797950d 0.600000000000 1638031 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": 1152444, "vin": [ { "gen": { "height": 1152434 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56b4616938b29f9500ed2ba97add896e1a09f9bef3790f391dcb5b7bd797950d" } } ], "extra": [ 1, 143, 117, 226, 183, 164, 248, 179, 182, 78, 14, 221, 110, 51, 128, 93, 148, 252, 201, 12, 27, 21, 198, 49, 169, 168, 57, 10, 169, 207, 248, 101, 132, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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