Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b158f5c5759d9daa3d134f3651d1d672d6d7010d452386e596888e8ade4eebe

Tx prefix hash: bf9e1bd1759795b3c4fcd9395a3a707faefee34183213bf529a273121a647f9d
Tx public key: cc68c841b527fd48d897f167cedbe2f14341dffc74f0dcb4de33e0d6ea24a241
Timestamp: 1706913712 Timestamp [UCT]: 2024-02-02 22:41:52 Age [y:d:h:m:s]: 01:304:11:28:07
Block: 949047 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 476434 RingCT/type: yes/0
Extra: 01cc68c841b527fd48d897f167cedbe2f14341dffc74f0dcb4de33e0d6ea24a2410211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4e0d353ab2e16eb86b5e8420765fa74f884260e7a617fc3479c70652cba2790 0.600000000000 1407569 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": 949057, "vin": [ { "gen": { "height": 949047 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4e0d353ab2e16eb86b5e8420765fa74f884260e7a617fc3479c70652cba2790" } } ], "extra": [ 1, 204, 104, 200, 65, 181, 39, 253, 72, 216, 151, 241, 103, 206, 219, 226, 241, 67, 65, 223, 252, 116, 240, 220, 180, 222, 51, 224, 214, 234, 36, 162, 65, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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