Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67e07edf8234fed17a3f6302c66eb0d58a3b7eb7165a33ca0eab6b9b8adaa502

Tx prefix hash: 6e94255743947d7057e14876cfeb1c2887e21a307aa615c6b1d8f0921f614670
Tx public key: 12f698f8b0fa5ed0da579515669c16ed62ad7207c74ff2c5b333794ab1f8a06e
Timestamp: 1710136747 Timestamp [UCT]: 2024-03-11 05:59:07 Age [y:d:h:m:s]: 01:052:18:35:35
Block: 975795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298717 RingCT/type: yes/0
Extra: 0112f698f8b0fa5ed0da579515669c16ed62ad7207c74ff2c5b333794ab1f8a06e0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd0d269f0701a82ca9b4dc9db20c662d9dfe1caec9281763dd5e9d15009c773f 0.600000000000 1435770 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": 975805, "vin": [ { "gen": { "height": 975795 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd0d269f0701a82ca9b4dc9db20c662d9dfe1caec9281763dd5e9d15009c773f" } } ], "extra": [ 1, 18, 246, 152, 248, 176, 250, 94, 208, 218, 87, 149, 21, 102, 156, 22, 237, 98, 173, 114, 7, 199, 79, 242, 197, 179, 51, 121, 74, 177, 248, 160, 110, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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