Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c900fb235435f7bd63dba91415df10c9e47ed854d78c964cd311d86d858392da

Tx prefix hash: b45d87d0b1e3f5589e3e29e1aa45f2e8f22319ba66eb7cd3733bf2cbf36a995a
Tx public key: 699917c22fd06ea2fdc07fb003c0512e82cf4fdd9a1b2b9f4c23ce5d31b161e9
Timestamp: 1673215954 Timestamp [UCT]: 2023-01-08 22:12:34 Age [y:d:h:m:s]: 02:139:23:37:51
Block: 670545 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 621774 RingCT/type: yes/0
Extra: 01699917c22fd06ea2fdc07fb003c0512e82cf4fdd9a1b2b9f4c23ce5d31b161e902110000000152542ceb000000000000000000

1 output(s) for total of 3.683036433000 dcy

stealth address amount amount idx
00: 0ce4e7a23ea33432429ccb862d6cf14e112555eb3eaa604ab2e44d58a91bfb7c 3.683036433000 1111956 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": 670555, "vin": [ { "gen": { "height": 670545 } } ], "vout": [ { "amount": 3683036433, "target": { "key": "0ce4e7a23ea33432429ccb862d6cf14e112555eb3eaa604ab2e44d58a91bfb7c" } } ], "extra": [ 1, 105, 153, 23, 194, 47, 208, 110, 162, 253, 192, 127, 176, 3, 192, 81, 46, 130, 207, 79, 221, 154, 27, 43, 159, 76, 35, 206, 93, 49, 177, 97, 233, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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