Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2ae117269e1d7077cb49f2ba924bf7b0297baddb94da9088686142b107e4885

Tx prefix hash: 448c956e49ed2b917ea4960b9221f547d68dea38dd21b3fa5ca265ed2278e9a6
Tx public key: fb0628c5e20327a4a18e3e61c0321160e4ab750e56c91aeaf599379b7f6d06ac
Timestamp: 1698569271 Timestamp [UCT]: 2023-10-29 08:47:51 Age [y:d:h:m:s]: 01:161:20:01:11
Block: 880101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376642 RingCT/type: yes/0
Extra: 01fb0628c5e20327a4a18e3e61c0321160e4ab750e56c91aeaf599379b7f6d06ac021100000002faf35c9c000000000000000000

1 output(s) for total of 0.744492029000 dcy

stealth address amount amount idx
00: d06ee3dede2ebacb64c7c95e70ed38d85af540314878322d546857a950f75663 0.744492029000 1335643 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": 880111, "vin": [ { "gen": { "height": 880101 } } ], "vout": [ { "amount": 744492029, "target": { "key": "d06ee3dede2ebacb64c7c95e70ed38d85af540314878322d546857a950f75663" } } ], "extra": [ 1, 251, 6, 40, 197, 226, 3, 39, 164, 161, 142, 62, 97, 192, 50, 17, 96, 228, 171, 117, 14, 86, 201, 26, 234, 245, 153, 55, 155, 127, 109, 6, 172, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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