Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b3c43c9ddf632e8551ff2b6f402655935fc9e3b67a0b4906844ab07ac31f850

Tx prefix hash: e4d0e572134b476e198b66de9d32467ec54110782a245f167fbc0d384ddfe884
Tx public key: 0d1ab87e2e88c2d9b422c96254c9e94b851b9ea7664875fd37db798c15d2de11
Timestamp: 1702306548 Timestamp [UCT]: 2023-12-11 14:55:48 Age [y:d:h:m:s]: 00:339:19:17:29
Block: 910869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243311 RingCT/type: yes/0
Extra: 010d1ab87e2e88c2d9b422c96254c9e94b851b9ea7664875fd37db798c15d2de11021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2fabf397f6dc867217d6b97897a94b167a24cc419170485d97dd703815272bd9 0.600000000000 1368044 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": 910879, "vin": [ { "gen": { "height": 910869 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2fabf397f6dc867217d6b97897a94b167a24cc419170485d97dd703815272bd9" } } ], "extra": [ 1, 13, 26, 184, 126, 46, 136, 194, 217, 180, 34, 201, 98, 84, 201, 233, 75, 133, 27, 158, 167, 102, 72, 117, 253, 55, 219, 121, 140, 21, 210, 222, 17, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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