Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5ca7af4f10af6a4b5c1c5b029fecfd9ba9bbd27634ef964b41cd7b796a624cf

Tx prefix hash: 2499419cb6f034dc62b9eb67d27ae3fbcfd4180830ce5ee92ecd3ec3e0d4ca07
Tx public key: 611ed7664611e65f4cedf735fac039e7f524240da8f331d2be0d1e6adc11ef2b
Timestamp: 1699687625 Timestamp [UCT]: 2023-11-11 07:27:05 Age [y:d:h:m:s]: 01:156:03:14:22
Block: 889161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372773 RingCT/type: yes/0
Extra: 01611ed7664611e65f4cedf735fac039e7f524240da8f331d2be0d1e6adc11ef2b02110000000333af99f4000000000000000000

1 output(s) for total of 0.694769105000 dcy

stealth address amount amount idx
00: 694c00cbcc51cec6465fbe2cf3c68e24079fc1fb90d11ea1a4bd1d8ca99e7182 0.694769105000 1345138 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": 889171, "vin": [ { "gen": { "height": 889161 } } ], "vout": [ { "amount": 694769105, "target": { "key": "694c00cbcc51cec6465fbe2cf3c68e24079fc1fb90d11ea1a4bd1d8ca99e7182" } } ], "extra": [ 1, 97, 30, 215, 102, 70, 17, 230, 95, 76, 237, 247, 53, 250, 192, 57, 231, 245, 36, 36, 13, 168, 243, 49, 210, 190, 13, 30, 106, 220, 17, 239, 43, 2, 17, 0, 0, 0, 3, 51, 175, 153, 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