Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6a47b08b1f9412e467908d5e63643e82e7b3d5a474a9319504d3522f85168b5

Tx prefix hash: 220baacb20f50776c626f4e5b058ae494606ef4b0119e6378feb51f5311af381
Tx public key: 478d8d867dac341c6905a1ecadbbdc6dd7d4b2a5ecd80b1e96e919d111542be2
Timestamp: 1646090661 Timestamp [UCT]: 2022-02-28 23:24:21 Age [y:d:h:m:s]: 02:349:20:49:55
Block: 448658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 769233 RingCT/type: yes/0
Extra: 01478d8d867dac341c6905a1ecadbbdc6dd7d4b2a5ecd80b1e96e919d111542be2021100000006c9067537000000000000000000

1 output(s) for total of 20.017511189000 dcy

stealth address amount amount idx
00: babec1705ce6c8ecfc22fb17a1d5cf2020688009ef6e8393be451650eb2b28a3 20.017511189000 863083 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": 448668, "vin": [ { "gen": { "height": 448658 } } ], "vout": [ { "amount": 20017511189, "target": { "key": "babec1705ce6c8ecfc22fb17a1d5cf2020688009ef6e8393be451650eb2b28a3" } } ], "extra": [ 1, 71, 141, 141, 134, 125, 172, 52, 28, 105, 5, 161, 236, 173, 187, 220, 109, 215, 212, 178, 165, 236, 216, 11, 30, 150, 233, 25, 209, 17, 84, 43, 226, 2, 17, 0, 0, 0, 6, 201, 6, 117, 55, 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