Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ab8dc0f938d41ecbbf84885322a881c8deda4250e7b1e4ee61bd893f5f82a3e

Tx prefix hash: d5bf952d12e57b9b8f9ac7b8d0e8a619a89d8eb84da5bf2da72bec117d636779
Tx public key: 9fc27a0adfefe8363aa96ef4c376f6b4ad528eac319ba1c318a87351653951be
Timestamp: 1577992869 Timestamp [UCT]: 2020-01-02 19:21:09 Age [y:d:h:m:s]: 05:112:21:53:30
Block: 37394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1230458 RingCT/type: yes/0
Extra: 019fc27a0adfefe8363aa96ef4c376f6b4ad528eac319ba1c318a87351653951be02110000004cd81c26c0000000000000000000

1 output(s) for total of 461.422753489000 dcy

stealth address amount amount idx
00: 67767551acb8b9739d1c5a2569dbc6e4c7950ca28fd7252dc9976df305a3bea6 461.422753489000 63458 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": 37404, "vin": [ { "gen": { "height": 37394 } } ], "vout": [ { "amount": 461422753489, "target": { "key": "67767551acb8b9739d1c5a2569dbc6e4c7950ca28fd7252dc9976df305a3bea6" } } ], "extra": [ 1, 159, 194, 122, 10, 223, 239, 232, 54, 58, 169, 110, 244, 195, 118, 246, 180, 173, 82, 142, 172, 49, 155, 161, 195, 24, 168, 115, 81, 101, 57, 81, 190, 2, 17, 0, 0, 0, 76, 216, 28, 38, 192, 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