Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: caee46a2a00a45a7980525b5d7c3af18dcefebdd7c354322cfbdccec15c642aa

Tx prefix hash: 21024c07372bac6ad9b727f5d3c6afd123f68e163cd1a0dca6b4a2073547f31d
Tx public key: 5b1bdbd6a8dbe5b3e1d33e2a19186e561205396fcce22c0cdb90673fd2ab4454
Timestamp: 1714942291 Timestamp [UCT]: 2024-05-05 20:51:31 Age [y:d:h:m:s]: 00:193:05:48:31
Block: 1015635 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138304 RingCT/type: yes/0
Extra: 015b1bdbd6a8dbe5b3e1d33e2a19186e561205396fcce22c0cdb90673fd2ab44540211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 548b871d70bf78cb8853763a9d615d4ce6abb532646a9b43b333b1dac5eb128d 0.600000000000 1479058 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": 1015645, "vin": [ { "gen": { "height": 1015635 } } ], "vout": [ { "amount": 600000000, "target": { "key": "548b871d70bf78cb8853763a9d615d4ce6abb532646a9b43b333b1dac5eb128d" } } ], "extra": [ 1, 91, 27, 219, 214, 168, 219, 229, 179, 225, 211, 62, 42, 25, 24, 110, 86, 18, 5, 57, 111, 204, 226, 44, 12, 219, 144, 103, 63, 210, 171, 68, 84, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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