Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61d7dbf5546cc527149e19950ef876d2671a07609cd490179042106487061dc7

Tx prefix hash: 0920fb6af53f814c61a44cf0632d1546d25041fee70a4b8f0e6139bbcc4b8091
Tx public key: b0de63cc9a58c03b93105f9040cfc12a2c8db8642b1ba2cc3fb3b5a2214af391
Timestamp: 1735515667 Timestamp [UCT]: 2024-12-29 23:41:07 Age [y:d:h:m:s]: 00:315:07:00:02
Block: 1186048 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222854 RingCT/type: yes/0
Extra: 01b0de63cc9a58c03b93105f9040cfc12a2c8db8642b1ba2cc3fb3b5a2214af3910211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de13c9c9725170b8df43af8b48d2cafb33ad2da429e4a3fa6cd27c625b5e312b 0.600000000000 1672523 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": 1186058, "vin": [ { "gen": { "height": 1186048 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de13c9c9725170b8df43af8b48d2cafb33ad2da429e4a3fa6cd27c625b5e312b" } } ], "extra": [ 1, 176, 222, 99, 204, 154, 88, 192, 59, 147, 16, 95, 144, 64, 207, 193, 42, 44, 141, 184, 100, 43, 27, 162, 204, 63, 179, 181, 162, 33, 74, 243, 145, 2, 17, 0, 0, 0, 1, 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