Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2753e8fb3cf139a746772a6099d35beefccb76da69f53240e7e727e093a2705

Tx prefix hash: df34761ab584d2f6f7d4527e3f8cef74c899521e457c455e4aadd07d774d9d74
Tx public key: 0d9779d535d3f9e832b01adf47aa37fbacab3d0e6712e04068c2610fe606de90
Timestamp: 1648686703 Timestamp [UCT]: 2022-03-31 00:31:43 Age [y:d:h:m:s]: 03:215:02:29:37
Block: 469934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 931716 RingCT/type: yes/0
Extra: 010d9779d535d3f9e832b01adf47aa37fbacab3d0e6712e04068c2610fe606de900211000000015eb576c5000000000000000000

1 output(s) for total of 17.018208051000 dcy

stealth address amount amount idx
00: 743a83509b459e5ee6be5e1c045e7c3df0ea1fc3878b68e5ea0ca1e58d9dfbe1 17.018208051000 888980 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": 469944, "vin": [ { "gen": { "height": 469934 } } ], "vout": [ { "amount": 17018208051, "target": { "key": "743a83509b459e5ee6be5e1c045e7c3df0ea1fc3878b68e5ea0ca1e58d9dfbe1" } } ], "extra": [ 1, 13, 151, 121, 213, 53, 211, 249, 232, 50, 176, 26, 223, 71, 170, 55, 251, 172, 171, 61, 14, 103, 18, 224, 64, 104, 194, 97, 15, 230, 6, 222, 144, 2, 17, 0, 0, 0, 1, 94, 181, 118, 197, 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