Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73e917f9a0895d9925c56a2c057f1f1773072b43c60f3608f947ee57eb0eb6fa

Tx prefix hash: b10a66612c4bc89718181bf1035a095cc726728633a307df97c4cf2332a086ed
Tx public key: 783700cd90785fd402a8bcc46dd4f581ccb02752ac6dc8a741e3579861b71f1a
Timestamp: 1702846793 Timestamp [UCT]: 2023-12-17 20:59:53 Age [y:d:h:m:s]: 02:018:07:38:02
Block: 915347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 532889 RingCT/type: yes/0
Extra: 01783700cd90785fd402a8bcc46dd4f581ccb02752ac6dc8a741e3579861b71f1a02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a4c6eaa3e5cb2a01b6c6b55a3c5a752ecea6d493d23a61e280d83d2ea106791 0.600000000000 1372741 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": 915357, "vin": [ { "gen": { "height": 915347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a4c6eaa3e5cb2a01b6c6b55a3c5a752ecea6d493d23a61e280d83d2ea106791" } } ], "extra": [ 1, 120, 55, 0, 205, 144, 120, 95, 212, 2, 168, 188, 196, 109, 212, 245, 129, 204, 176, 39, 82, 172, 109, 200, 167, 65, 227, 87, 152, 97, 183, 31, 26, 2, 17, 0, 0, 0, 1, 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