Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00b7c5cadaffbf1e913cc1728495b4e438dbf2edcb2ce98bee01c6b0b82b9c91

Tx prefix hash: 01c38e122aa81fb5177b097d9538fc2dccd2c16284b99c9656554730891464b9
Tx public key: eded8c5f3345f856c096a1519de818319b310f8b5e07981ff528f238461b28cf
Timestamp: 1713402317 Timestamp [UCT]: 2024-04-18 01:05:17 Age [y:d:h:m:s]: 00:332:14:47:58
Block: 1002838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237813 RingCT/type: yes/0
Extra: 01eded8c5f3345f856c096a1519de818319b310f8b5e07981ff528f238461b28cf02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 667675dc8285fdf9296aa320f1eec0c360f45698cf3ca51608ae1b1d8b66b981 0.600000000000 1463366 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": 1002848, "vin": [ { "gen": { "height": 1002838 } } ], "vout": [ { "amount": 600000000, "target": { "key": "667675dc8285fdf9296aa320f1eec0c360f45698cf3ca51608ae1b1d8b66b981" } } ], "extra": [ 1, 237, 237, 140, 95, 51, 69, 248, 86, 192, 150, 161, 81, 157, 232, 24, 49, 155, 49, 15, 139, 94, 7, 152, 31, 245, 40, 242, 56, 70, 27, 40, 207, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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