Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1d32530c9ddbe0216664302ab2ecd1cfc30dcbec66040cbe94094a1460e8dca

Tx prefix hash: e5f3cd83a301588d95338a730c453d7beb5521e09dc6ce21602926a7ea974c7e
Tx public key: 4ddd91f9f0e69c4f60e962717eb4c265e080e18723067bbaac62a0a69592e718
Timestamp: 1736926674 Timestamp [UCT]: 2025-01-15 07:37:54 Age [y:d:h:m:s]: 00:153:19:05:52
Block: 1197734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109623 RingCT/type: yes/0
Extra: 014ddd91f9f0e69c4f60e962717eb4c265e080e18723067bbaac62a0a69592e71802110000000c007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93e8cbfd417c27e9e53652eeeb39f2287704658ab7f1e000dc9f6e95b0a106dc 0.600000000000 1684349 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": 1197744, "vin": [ { "gen": { "height": 1197734 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93e8cbfd417c27e9e53652eeeb39f2287704658ab7f1e000dc9f6e95b0a106dc" } } ], "extra": [ 1, 77, 221, 145, 249, 240, 230, 156, 79, 96, 233, 98, 113, 126, 180, 194, 101, 224, 128, 225, 135, 35, 6, 123, 186, 172, 98, 160, 166, 149, 146, 231, 24, 2, 17, 0, 0, 0, 12, 0, 127, 151, 138, 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