Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4ac225059e5e69ae60511e785775b8341dd97d6d8491771b8bb85350f3ef85a

Tx prefix hash: fd6dcfdf8d104be3745ecf2d104e8374f9150e74e9b393605b5ef03a364eeba8
Tx public key: e53abbdb8a395ca8c3a2b7e906f2f27ca75b519c4e7180aae705744ccbc62c77
Timestamp: 1721949882 Timestamp [UCT]: 2024-07-25 23:24:42 Age [y:d:h:m:s]: 00:280:05:45:42
Block: 1073716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200216 RingCT/type: yes/0
Extra: 01e53abbdb8a395ca8c3a2b7e906f2f27ca75b519c4e7180aae705744ccbc62c77021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e0dbedb0f51dfc0ea13df750fa726046ef5cf0aae7bb35ba7aabc033024de33 0.600000000000 1546223 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": 1073726, "vin": [ { "gen": { "height": 1073716 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e0dbedb0f51dfc0ea13df750fa726046ef5cf0aae7bb35ba7aabc033024de33" } } ], "extra": [ 1, 229, 58, 187, 219, 138, 57, 92, 168, 195, 162, 183, 233, 6, 242, 242, 124, 167, 91, 81, 156, 78, 113, 128, 170, 231, 5, 116, 76, 203, 198, 44, 119, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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