Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e168ee9035b21555d788d482c20adeadfae35dfe9405891da60ce3f1b0fea1bb

Tx prefix hash: 1ca24ef734d0aa56d737ed5b1099ff210e3857ba290ee889f2aa7b361a057f2e
Tx public key: 329f26542b91c23d5eb33263678f7a1f3901e2959e51d02bd4f7212eb843a712
Timestamp: 1672882195 Timestamp [UCT]: 2023-01-05 01:29:55 Age [y:d:h:m:s]: 02:096:07:35:49
Block: 667788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 590527 RingCT/type: yes/0
Extra: 01329f26542b91c23d5eb33263678f7a1f3901e2959e51d02bd4f7212eb843a71202110000000352542ceb000000000000000000

1 output(s) for total of 3.761327113000 dcy

stealth address amount amount idx
00: 48d1d9de6e0e9b4f06b3a2039fe28d4fb1ff828d7cb285f1bd7227f9ac34c313 3.761327113000 1109007 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": 667798, "vin": [ { "gen": { "height": 667788 } } ], "vout": [ { "amount": 3761327113, "target": { "key": "48d1d9de6e0e9b4f06b3a2039fe28d4fb1ff828d7cb285f1bd7227f9ac34c313" } } ], "extra": [ 1, 50, 159, 38, 84, 43, 145, 194, 61, 94, 179, 50, 99, 103, 143, 122, 31, 57, 1, 226, 149, 158, 81, 208, 43, 212, 247, 33, 46, 184, 67, 167, 18, 2, 17, 0, 0, 0, 3, 82, 84, 44, 235, 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