Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 457f1607a52ded5a044b6717d80076638cb19c95b84a47e325fe78aa324a1da1

Tx prefix hash: 31b609654a4ac9a55e72a1a5f555e6712fa54d1dd0a60ee9784247aac43db361
Tx public key: e9c1fe5849dfcda9481ce8f5fa624bb4dfb6793baed0f23338f610d55b12fbf7
Timestamp: 1722436450 Timestamp [UCT]: 2024-07-31 14:34:10 Age [y:d:h:m:s]: 00:297:09:35:28
Block: 1077750 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212497 RingCT/type: yes/0
Extra: 01e9c1fe5849dfcda9481ce8f5fa624bb4dfb6793baed0f23338f610d55b12fbf702110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86ea90ed704f48cbfb94a7c6b3b0dbde78337e4cacc01c64fecf3ad1584e5188 0.600000000000 1550305 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": 1077760, "vin": [ { "gen": { "height": 1077750 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86ea90ed704f48cbfb94a7c6b3b0dbde78337e4cacc01c64fecf3ad1584e5188" } } ], "extra": [ 1, 233, 193, 254, 88, 73, 223, 205, 169, 72, 28, 232, 245, 250, 98, 75, 180, 223, 182, 121, 59, 174, 208, 242, 51, 56, 246, 16, 213, 91, 18, 251, 247, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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