Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac5bdcba488cf2872e318f5d219c5b85094241049dbf62329c295a3680c9e01d

Tx prefix hash: 9de99f0e7409106ddb2d82bdf74460b716b5a042eb65f417748755625d27fd0d
Tx public key: d6f5cf9884116b5388dbb931589d7e236f604bed0c5646abb96608e1929a82d6
Timestamp: 1699402811 Timestamp [UCT]: 2023-11-08 00:20:11 Age [y:d:h:m:s]: 01:017:07:55:28
Block: 886795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273764 RingCT/type: yes/0
Extra: 01d6f5cf9884116b5388dbb931589d7e236f604bed0c5646abb96608e1929a82d602110000000475e3f0e9000000000000000000

1 output(s) for total of 0.707424411000 dcy

stealth address amount amount idx
00: 47cb5ba15dba75c8e4ff29471f3a3abc9b8ab381c5cf85fed2604f746cae6343 0.707424411000 1342638 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": 886805, "vin": [ { "gen": { "height": 886795 } } ], "vout": [ { "amount": 707424411, "target": { "key": "47cb5ba15dba75c8e4ff29471f3a3abc9b8ab381c5cf85fed2604f746cae6343" } } ], "extra": [ 1, 214, 245, 207, 152, 132, 17, 107, 83, 136, 219, 185, 49, 88, 157, 126, 35, 111, 96, 75, 237, 12, 86, 70, 171, 185, 102, 8, 225, 146, 154, 130, 214, 2, 17, 0, 0, 0, 4, 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