Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77a8716ef0d49a4f9df9910aeb24da53327d63ae9f29d860427b4e92f710c4c9

Tx prefix hash: 8ffad907a1caafe4b363228ddd834e80930cd81df29eb1025c6d766b386432c5
Tx public key: d95ac2020699e1b8e0eb244a6439f8e8a829f8d4855150f48a4ac1b4c17a44aa
Timestamp: 1643502848 Timestamp [UCT]: 2022-01-30 00:34:08 Age [y:d:h:m:s]: 03:279:08:55:52
Block: 428126 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 976573 RingCT/type: yes/0
Extra: 01d95ac2020699e1b8e0eb244a6439f8e8a829f8d4855150f48a4ac1b4c17a44aa0211000000012e6b1fd5000000000000000000

1 output(s) for total of 23.412141985000 dcy

stealth address amount amount idx
00: 6111226b5fa12ca6581363a87d04982b0c588ef48bc5085e38b4055990b48541 23.412141985000 837444 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": 428136, "vin": [ { "gen": { "height": 428126 } } ], "vout": [ { "amount": 23412141985, "target": { "key": "6111226b5fa12ca6581363a87d04982b0c588ef48bc5085e38b4055990b48541" } } ], "extra": [ 1, 217, 90, 194, 2, 6, 153, 225, 184, 224, 235, 36, 74, 100, 57, 248, 232, 168, 41, 248, 212, 133, 81, 80, 244, 138, 74, 193, 180, 193, 122, 68, 170, 2, 17, 0, 0, 0, 1, 46, 107, 31, 213, 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