Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b58c2face808582b88b9fbabaf0e0c5b6533465b89b51c7e2fd0f4f7fc81f88d

Tx prefix hash: d218af2ee28c1d5a0ebddcf0eeade3616627f5bfa5880ba4353d3c874c30a4ee
Tx public key: b9865a672eddd6c9f898f4d2f816b3ccfa7f5db0723e5d40c99c5ad5fc08d878
Timestamp: 1702965647 Timestamp [UCT]: 2023-12-19 06:00:47 Age [y:d:h:m:s]: 01:071:03:23:35
Block: 916340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311934 RingCT/type: yes/0
Extra: 01b9865a672eddd6c9f898f4d2f816b3ccfa7f5db0723e5d40c99c5ad5fc08d87802110000000775e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e1e3f9ac4a37ae1c93d2fe6141bd65368f4d1189bfef27d41ea4e5da4e3fd29 0.600000000000 1373840 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": 916350, "vin": [ { "gen": { "height": 916340 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e1e3f9ac4a37ae1c93d2fe6141bd65368f4d1189bfef27d41ea4e5da4e3fd29" } } ], "extra": [ 1, 185, 134, 90, 103, 46, 221, 214, 201, 248, 152, 244, 210, 248, 22, 179, 204, 250, 127, 93, 176, 114, 62, 93, 64, 201, 156, 90, 213, 252, 8, 216, 120, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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