Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f630fc6723bcf9bc869dd369b1d79762aaee90c605a617cec84b8f60d8dd31ad

Tx prefix hash: 2444ad2122680a764ff4fd222cd76cf76ab30fafbb05783f653df7a3f1bbbacd
Tx public key: 7c53819082e4542f9688bd2c046a52201d2d5dd1e933cff18f314ac7c2e3f0b2
Timestamp: 1720870025 Timestamp [UCT]: 2024-07-13 11:27:05 Age [y:d:h:m:s]: 00:224:16:29:04
Block: 1064779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160462 RingCT/type: yes/0
Extra: 017c53819082e4542f9688bd2c046a52201d2d5dd1e933cff18f314ac7c2e3f0b202110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c72ab2e228511de52b6f21d0059a3724fae9e0e35906b3c14be27f25f01403ca 0.600000000000 1535318 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": 1064789, "vin": [ { "gen": { "height": 1064779 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c72ab2e228511de52b6f21d0059a3724fae9e0e35906b3c14be27f25f01403ca" } } ], "extra": [ 1, 124, 83, 129, 144, 130, 228, 84, 47, 150, 136, 189, 44, 4, 106, 82, 32, 29, 45, 93, 209, 233, 51, 207, 241, 143, 49, 74, 199, 194, 227, 240, 178, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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