Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32315cc60cd357dd647037dc8626a5ad314cd9afaa8fde96eff8a2d37a5415ce

Tx prefix hash: 3af7cab6d0459b1a761bed738b4499b90be4390cca03ee46bcb2d905e8b21bca
Tx public key: 3e37a9d7b80a959414fa7fef1e5f21a6038ee80e4b03c27e8d9df81732f068ef
Timestamp: 1699759414 Timestamp [UCT]: 2023-11-12 03:23:34 Age [y:d:h:m:s]: 01:002:08:14:21
Block: 889752 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263039 RingCT/type: yes/0
Extra: 013e37a9d7b80a959414fa7fef1e5f21a6038ee80e4b03c27e8d9df81732f068ef02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.691643451000 dcy

stealth address amount amount idx
00: 022600b0e320903ded8cb2df7dc8197aa1fd0d958b8724626a0a2dc8030f684d 0.691643451000 1345765 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": 889762, "vin": [ { "gen": { "height": 889752 } } ], "vout": [ { "amount": 691643451, "target": { "key": "022600b0e320903ded8cb2df7dc8197aa1fd0d958b8724626a0a2dc8030f684d" } } ], "extra": [ 1, 62, 55, 169, 215, 184, 10, 149, 148, 20, 250, 127, 239, 30, 95, 33, 166, 3, 142, 232, 14, 75, 3, 194, 126, 141, 157, 248, 23, 50, 240, 104, 239, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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