Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81e8ba8e2702a120e64ff2c791f12fc7f0f45904b0f7c451275c1e69a2b48ecc

Tx prefix hash: 4f3488bf281273556205fa9743f31572697225215e882a1811f9ed7fd8321943
Tx public key: c94f65dfb8fc0c470c9cb2fa3114b08e5c1a1135ec1727d52dd3a91ed82f9ae6
Timestamp: 1673488512 Timestamp [UCT]: 2023-01-12 01:55:12 Age [y:d:h:m:s]: 01:325:06:01:37
Block: 672805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 493480 RingCT/type: yes/0
Extra: 01c94f65dfb8fc0c470c9cb2fa3114b08e5c1a1135ec1727d52dd3a91ed82f9ae60211000000018b7b6602000000000000000000

1 output(s) for total of 3.620076044000 dcy

stealth address amount amount idx
00: 1a4203ab2f13e05d31dfc44105ad7203fc331ab9bd6e4aa0b795e4224f309c4c 3.620076044000 1114370 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": 672815, "vin": [ { "gen": { "height": 672805 } } ], "vout": [ { "amount": 3620076044, "target": { "key": "1a4203ab2f13e05d31dfc44105ad7203fc331ab9bd6e4aa0b795e4224f309c4c" } } ], "extra": [ 1, 201, 79, 101, 223, 184, 252, 12, 71, 12, 156, 178, 250, 49, 20, 176, 142, 92, 26, 17, 53, 236, 23, 39, 213, 45, 211, 169, 30, 216, 47, 154, 230, 2, 17, 0, 0, 0, 1, 139, 123, 102, 2, 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