Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba84d61dbe02a916251bc7f7c65cdf08a8c3b1370756a5eb691a90d46e99e337

Tx prefix hash: 00103b64389b588823182a5445814a129c3535bdc772fa9c83321ae79b1fd995
Tx public key: f1a8e594258a9def79344b66713d156b5399e793186cb696b63a2c55b7d6fd20
Timestamp: 1729525288 Timestamp [UCT]: 2024-10-21 15:41:28 Age [y:d:h:m:s]: 00:033:22:11:00
Block: 1136485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24245 RingCT/type: yes/0
Extra: 01f1a8e594258a9def79344b66713d156b5399e793186cb696b63a2c55b7d6fd200211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03b182400a1db971c1e6f1f524a6caefe28a96bbc8c116fb5d2515f06d89d5cb 0.600000000000 1619830 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": 1136495, "vin": [ { "gen": { "height": 1136485 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03b182400a1db971c1e6f1f524a6caefe28a96bbc8c116fb5d2515f06d89d5cb" } } ], "extra": [ 1, 241, 168, 229, 148, 37, 138, 157, 239, 121, 52, 75, 102, 113, 61, 21, 107, 83, 153, 231, 147, 24, 108, 182, 150, 182, 58, 44, 85, 183, 214, 253, 32, 2, 17, 0, 0, 0, 6, 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