Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de8ea21cbe887a18adb6c241b72832270f0cf5411a3de43d4edcb35b5c0e0f1c

Tx prefix hash: 038688827258aa19e2e36cc525986919ddcce8feacff6efec4250cdb3053ac46
Tx public key: fbf66d1b61dee5393b99f2aa7637190176d8532af33fb6331cb2a40d26f87690
Timestamp: 1706817204 Timestamp [UCT]: 2024-02-01 19:53:24 Age [y:d:h:m:s]: 00:349:02:59:15
Block: 948248 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249943 RingCT/type: yes/0
Extra: 01fbf66d1b61dee5393b99f2aa7637190176d8532af33fb6331cb2a40d26f8769002110000000610a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 032a8bb34c21bfc9660910bded4b830f9fcdc8e1eac5c5a3fbc7c6726bbd701c 0.600000000000 1406622 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": 948258, "vin": [ { "gen": { "height": 948248 } } ], "vout": [ { "amount": 600000000, "target": { "key": "032a8bb34c21bfc9660910bded4b830f9fcdc8e1eac5c5a3fbc7c6726bbd701c" } } ], "extra": [ 1, 251, 246, 109, 27, 97, 222, 229, 57, 59, 153, 242, 170, 118, 55, 25, 1, 118, 216, 83, 42, 243, 63, 182, 51, 28, 178, 164, 13, 38, 248, 118, 144, 2, 17, 0, 0, 0, 6, 16, 161, 116, 143, 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