Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ec60a9b3faa23cee0133d823d7b7d9d70ccd8ceb3197b29d01905dbdc659d81

Tx prefix hash: 1a19504b0ad1b56949d6f6da8ec03172a680e285e2f7d77251e5fa7e83a2d0fe
Tx public key: 38b4e9154166ab623dbe871a388b57dbcc66cd82b2bc3aca550b7384d3ccbcb6
Timestamp: 1707100679 Timestamp [UCT]: 2024-02-05 02:37:59 Age [y:d:h:m:s]: 00:351:21:25:16
Block: 950596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251885 RingCT/type: yes/0
Extra: 0138b4e9154166ab623dbe871a388b57dbcc66cd82b2bc3aca550b7384d3ccbcb60211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a113ea67787ece0e9f9fe51d9d83c7df6879b1aabc9febbfdfdf13b2a44bcb8 0.600000000000 1409238 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": 950606, "vin": [ { "gen": { "height": 950596 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a113ea67787ece0e9f9fe51d9d83c7df6879b1aabc9febbfdfdf13b2a44bcb8" } } ], "extra": [ 1, 56, 180, 233, 21, 65, 102, 171, 98, 61, 190, 135, 26, 56, 139, 87, 219, 204, 102, 205, 130, 178, 188, 58, 202, 85, 11, 115, 132, 211, 204, 188, 182, 2, 17, 0, 0, 0, 2, 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