Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: beff1bfc768c27bb9b118a4023fb41707f06deb0f35e910ab1d93537e61ede25

Tx prefix hash: 31755711017b5ebea8e9e9301bc284b67161f313d94d90cb5a72028f3c42a605
Tx public key: aff012415f53d2759b573fb7d8fbf084444a5d060a4fdb3396f52b5fcabdaa40
Timestamp: 1577653712 Timestamp [UCT]: 2019-12-29 21:08:32 Age [y:d:h:m:s]: 04:332:19:13:53
Block: 34553 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1126965 RingCT/type: yes/0
Extra: 01aff012415f53d2759b573fb7d8fbf084444a5d060a4fdb3396f52b5fcabdaa400211000000084943cd9f000000000000000000

1 output(s) for total of 471.594719342000 dcy

stealth address amount amount idx
00: 73caf693c356398b0122fa8f9310d724dddd5a1d76252eb0512c3b9e3e9e97a7 471.594719342000 58159 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": 34563, "vin": [ { "gen": { "height": 34553 } } ], "vout": [ { "amount": 471594719342, "target": { "key": "73caf693c356398b0122fa8f9310d724dddd5a1d76252eb0512c3b9e3e9e97a7" } } ], "extra": [ 1, 175, 240, 18, 65, 95, 83, 210, 117, 155, 87, 63, 183, 216, 251, 240, 132, 68, 74, 93, 6, 10, 79, 219, 51, 150, 245, 43, 95, 202, 189, 170, 64, 2, 17, 0, 0, 0, 8, 73, 67, 205, 159, 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