Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 215050ddc7e0e625923a75b20b4337b4f441ce78dd2767abbbc873e23aa653e1

Tx prefix hash: 61aa9ff9af51503ffc754a180d926106907c4da8f4b39a93453bebd6c5c8da04
Tx public key: 9c5a13db08e38ce8d7b128688d20dbae3cbcfd061ea9922cd6830e175b072a0e
Timestamp: 1697248685 Timestamp [UCT]: 2023-10-14 01:58:05 Age [y:d:h:m:s]: 01:096:19:10:54
Block: 869138 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330433 RingCT/type: yes/0
Extra: 019c5a13db08e38ce8d7b128688d20dbae3cbcfd061ea9922cd6830e175b072a0e02110000000633af99f4000000000000000000

1 output(s) for total of 0.809440701000 dcy

stealth address amount amount idx
00: e158c97a9371a420a32db97595c173bd8e0d657c1c29295dfea702fb549771a6 0.809440701000 1323973 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": 869148, "vin": [ { "gen": { "height": 869138 } } ], "vout": [ { "amount": 809440701, "target": { "key": "e158c97a9371a420a32db97595c173bd8e0d657c1c29295dfea702fb549771a6" } } ], "extra": [ 1, 156, 90, 19, 219, 8, 227, 140, 232, 215, 177, 40, 104, 141, 32, 219, 174, 60, 188, 253, 6, 30, 169, 146, 44, 214, 131, 14, 23, 91, 7, 42, 14, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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