Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: defb411c1c017a4a2cf38a0a66faec1ecb6029494997ae2022b228525b3ce39a

Tx prefix hash: e40df7d60007a43de90488b54aa71f50c6e88782912035daf22a743cf46fe5c5
Tx public key: 070fbc6460f2a16332a0bac80ad0a6df8cda5f8950fbf1bcebdfc7d5f735e7e1
Timestamp: 1715682141 Timestamp [UCT]: 2024-05-14 10:22:21 Age [y:d:h:m:s]: 01:028:17:06:55
Block: 1021764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281416 RingCT/type: yes/0
Extra: 01070fbc6460f2a16332a0bac80ad0a6df8cda5f8950fbf1bcebdfc7d5f735e7e1021100000003e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b36120f774937097aff901a1ebb734010f2e33a10ef8223f2156b3280dc0a34 0.600000000000 1486173 of 15

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": 1021774, "vin": [ { "gen": { "height": 1021764 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b36120f774937097aff901a1ebb734010f2e33a10ef8223f2156b3280dc0a34" } } ], "extra": [ 1, 7, 15, 188, 100, 96, 242, 161, 99, 50, 160, 186, 200, 10, 208, 166, 223, 140, 218, 95, 137, 80, 251, 241, 188, 235, 223, 199, 213, 247, 53, 231, 225, 2, 17, 0, 0, 0, 3, 224, 133, 50, 182, 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