Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2f3c93f6bc3af593b88a54521e28cce0da3a26efc9820e6cfdca69b0b1de85b

Tx prefix hash: 395d22810c9407b71572ae39792bd53470082a7fe44edb1210f4832169f8eb66
Tx public key: 2aec8aa4daf5ad3326a6a0b4ef2bd60ad6be9ea794c3a6b8054fbb7af0461374
Timestamp: 1588736975 Timestamp [UCT]: 2020-05-06 03:49:35 Age [y:d:h:m:s]: 04:352:12:17:16
Block: 99014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1168093 RingCT/type: yes/0
Extra: 012aec8aa4daf5ad3326a6a0b4ef2bd60ad6be9ea794c3a6b8054fbb7af046137402110000016f37fb5df4000000000000000000

1 output(s) for total of 288.354198148000 dcy

stealth address amount amount idx
00: 6157f587a402ae32d2d13e07d2e9193a757bff2ad1b7037c20b1dbc18e377221 288.354198148000 174848 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": 99024, "vin": [ { "gen": { "height": 99014 } } ], "vout": [ { "amount": 288354198148, "target": { "key": "6157f587a402ae32d2d13e07d2e9193a757bff2ad1b7037c20b1dbc18e377221" } } ], "extra": [ 1, 42, 236, 138, 164, 218, 245, 173, 51, 38, 166, 160, 180, 239, 43, 214, 10, 214, 190, 158, 167, 148, 195, 166, 184, 5, 79, 187, 122, 240, 70, 19, 116, 2, 17, 0, 0, 1, 111, 55, 251, 93, 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