Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b0d404ddeb09dbddd3f96504cc545f41cbb8f0d004e79e4e040dfe460dbb64d

Tx prefix hash: f0c9cc8ebf5fff034fabf6f0d98acf61e9d63fd243b88a6dd6ab5d523af0b43e
Tx public key: 5c13d94fb72bf88121db4c0f23ea7cf3f8e60f68e58d789cd2dfcf9699801390
Timestamp: 1672819401 Timestamp [UCT]: 2023-01-04 08:03:21 Age [y:d:h:m:s]: 02:117:12:07:35
Block: 667274 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 605670 RingCT/type: yes/0
Extra: 015c13d94fb72bf88121db4c0f23ea7cf3f8e60f68e58d789cd2dfcf9699801390021100000002faf35c9c000000000000000000

1 output(s) for total of 3.776106205000 dcy

stealth address amount amount idx
00: b010c373cb350e794b7be5e603707a77a55d35e74d399aa080a80bfd6b0456f0 3.776106205000 1108441 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": 667284, "vin": [ { "gen": { "height": 667274 } } ], "vout": [ { "amount": 3776106205, "target": { "key": "b010c373cb350e794b7be5e603707a77a55d35e74d399aa080a80bfd6b0456f0" } } ], "extra": [ 1, 92, 19, 217, 79, 183, 43, 248, 129, 33, 219, 76, 15, 35, 234, 124, 243, 248, 230, 15, 104, 229, 141, 120, 156, 210, 223, 207, 150, 153, 128, 19, 144, 2, 17, 0, 0, 0, 2, 250, 243, 92, 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