Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd3b4532a47424edbb7e249a7d44722b327924bda3803aa5945cc64a51d61404

Tx prefix hash: aa9a550df72de564a194bc2a9de793ed171935b677edfb251d0d892acf5345e1
Tx public key: f91fe9dcffb69a437bb348f5121fd0d8be026e31c6e19d495514dbd94de12809
Timestamp: 1708793396 Timestamp [UCT]: 2024-02-24 16:49:56 Age [y:d:h:m:s]: 01:046:15:59:32
Block: 964661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294363 RingCT/type: yes/0
Extra: 01f91fe9dcffb69a437bb348f5121fd0d8be026e31c6e19d495514dbd94de12809021100000003e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4718e0d811457dd75b15dda8b28f6f9d4f20675883ef33035a5e5e40e57fc4bc 0.600000000000 1424402 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": 964671, "vin": [ { "gen": { "height": 964661 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4718e0d811457dd75b15dda8b28f6f9d4f20675883ef33035a5e5e40e57fc4bc" } } ], "extra": [ 1, 249, 31, 233, 220, 255, 182, 154, 67, 123, 179, 72, 245, 18, 31, 208, 216, 190, 2, 110, 49, 198, 225, 157, 73, 85, 20, 219, 217, 77, 225, 40, 9, 2, 17, 0, 0, 0, 3, 224, 133, 50, 182, 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