Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdbaa11a3e41f3001c6f47823248c27bdfef98846f4b0b68d0ab2e654126709c

Tx prefix hash: 433e1389d5c5887a19bc4f8c1e17bc73ab7c7b2b50d500cda49f652f35744149
Tx public key: 149aea4c4fa167e2d70d39ea19904439558a532abd8dca27b470b4ef1399992c
Timestamp: 1582358060 Timestamp [UCT]: 2020-02-22 07:54:20 Age [y:d:h:m:s]: 05:011:12:17:19
Block: 70134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1161330 RingCT/type: yes/0
Extra: 01149aea4c4fa167e2d70d39ea19904439558a532abd8dca27b470b4ef1399992c02110000000ed81c26c0000000000000000000

1 output(s) for total of 359.457664263000 dcy

stealth address amount amount idx
00: 0741279816dc835e0af1ee70e346435a9e36abda383ac68895df003827cafd7e 359.457664263000 129462 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": 70144, "vin": [ { "gen": { "height": 70134 } } ], "vout": [ { "amount": 359457664263, "target": { "key": "0741279816dc835e0af1ee70e346435a9e36abda383ac68895df003827cafd7e" } } ], "extra": [ 1, 20, 154, 234, 76, 79, 161, 103, 226, 215, 13, 57, 234, 25, 144, 68, 57, 85, 138, 83, 42, 189, 141, 202, 39, 180, 112, 180, 239, 19, 153, 153, 44, 2, 17, 0, 0, 0, 14, 216, 28, 38, 192, 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