Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ac07e4bb5d0ec2c705eef53e3f631a890b327ebc0eec8eb6a41b40b276050f2

Tx prefix hash: 6cf049d754096a7d1e0a6ba364b435c33c48dd8c8fc5ce5c9a7b5828f1dc2999
Tx public key: f48069ebc0b0b48db08a3723e9cb1866f1ab4dd2aa65ec4e3f787aeb1aebd0eb
Timestamp: 1699635021 Timestamp [UCT]: 2023-11-10 16:50:21 Age [y:d:h:m:s]: 01:163:23:59:49
Block: 888727 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378403 RingCT/type: yes/0
Extra: 01f48069ebc0b0b48db08a3723e9cb1866f1ab4dd2aa65ec4e3f787aeb1aebd0eb02110000000afaf35c9c000000000000000000

1 output(s) for total of 0.697073416000 dcy

stealth address amount amount idx
00: a89768bb1566cb44c55c1e9d35d1b46f1db38ef36547af5bbcd1fb24480c1871 0.697073416000 1344682 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": 888737, "vin": [ { "gen": { "height": 888727 } } ], "vout": [ { "amount": 697073416, "target": { "key": "a89768bb1566cb44c55c1e9d35d1b46f1db38ef36547af5bbcd1fb24480c1871" } } ], "extra": [ 1, 244, 128, 105, 235, 192, 176, 180, 141, 176, 138, 55, 35, 233, 203, 24, 102, 241, 171, 77, 210, 170, 101, 236, 78, 63, 120, 122, 235, 26, 235, 208, 235, 2, 17, 0, 0, 0, 10, 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