Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc6ba2a843b00d4336425cd9bc6bfa1667a237460e0a15e2d96ff70ea636a8a3

Tx prefix hash: ac42eed900ea13040fb7b311f652bc20c3bda9704c75cd698e76273f5fe7940c
Tx public key: b663537e1aa7a7dbe44f62cf7382db67240a2d5d8754e88c57cf274de4aafc46
Timestamp: 1685114330 Timestamp [UCT]: 2023-05-26 15:18:50 Age [y:d:h:m:s]: 01:333:14:58:02
Block: 768579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 499669 RingCT/type: yes/0
Extra: 01b663537e1aa7a7dbe44f62cf7382db67240a2d5d8754e88c57cf274de4aafc46021100000004e6d27f9c000000000000000000

1 output(s) for total of 1.743327161000 dcy

stealth address amount amount idx
00: 0e0da7817f81428f588b1f93d0cbd6d03fcac2fbe3f785eb69fad70d647bb426 1.743327161000 1217786 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": 768589, "vin": [ { "gen": { "height": 768579 } } ], "vout": [ { "amount": 1743327161, "target": { "key": "0e0da7817f81428f588b1f93d0cbd6d03fcac2fbe3f785eb69fad70d647bb426" } } ], "extra": [ 1, 182, 99, 83, 126, 26, 167, 167, 219, 228, 79, 98, 207, 115, 130, 219, 103, 36, 10, 45, 93, 135, 84, 232, 140, 87, 207, 39, 77, 228, 170, 252, 70, 2, 17, 0, 0, 0, 4, 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