Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b46ffb41d96a383ec7a86bb3a3b7e6533c397513471221113ee2d8292e96adf

Tx prefix hash: 030a47cd8aa931c2b28c398c48d6b84442f73d2cd3f1348c0468fe2a552cef32
Tx public key: 809585b744f9beb3d9d99f031cb79fb58ae0ea637d51bae1afbbc08bae626903
Timestamp: 1694922055 Timestamp [UCT]: 2023-09-17 03:40:55 Age [y:d:h:m:s]: 01:128:23:32:28
Block: 849831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353458 RingCT/type: yes/0
Extra: 01809585b744f9beb3d9d99f031cb79fb58ae0ea637d51bae1afbbc08bae62690302110000000375e3f0e9000000000000000000

1 output(s) for total of 0.937901374000 dcy

stealth address amount amount idx
00: 049da9c1d2fb9eb98d9a9e8a0e98e142284155881411e0dc26b4752e6e49ffa2 0.937901374000 1303515 of 0

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": 849841, "vin": [ { "gen": { "height": 849831 } } ], "vout": [ { "amount": 937901374, "target": { "key": "049da9c1d2fb9eb98d9a9e8a0e98e142284155881411e0dc26b4752e6e49ffa2" } } ], "extra": [ 1, 128, 149, 133, 183, 68, 249, 190, 179, 217, 217, 159, 3, 28, 183, 159, 181, 138, 224, 234, 99, 125, 81, 186, 225, 175, 187, 192, 139, 174, 98, 105, 3, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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