Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf684d8e383145b0d6401174d25a1f88ad5d39bce5c8481cab10900a469f0dea

Tx prefix hash: e4f514c2c448e577c438c0ac9e8ba8349f3fc070c4579e4a84a3d10eca34840e
Tx public key: 3eff046c4ee00f0494868d1ef5f3c8da3795d9dd929cfbf3ca96593b296f055b
Timestamp: 1724338963 Timestamp [UCT]: 2024-08-22 15:02:43 Age [y:d:h:m:s]: 00:238:23:54:09
Block: 1093543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170674 RingCT/type: yes/0
Extra: 013eff046c4ee00f0494868d1ef5f3c8da3795d9dd929cfbf3ca96593b296f055b021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f1446bfda94c23d4cbc0fb0797bcb245cf4b5b1d6da645161a0e2d86e58c445 0.600000000000 1568508 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": 1093553, "vin": [ { "gen": { "height": 1093543 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f1446bfda94c23d4cbc0fb0797bcb245cf4b5b1d6da645161a0e2d86e58c445" } } ], "extra": [ 1, 62, 255, 4, 108, 78, 224, 15, 4, 148, 134, 141, 30, 245, 243, 200, 218, 55, 149, 217, 221, 146, 156, 251, 243, 202, 150, 89, 59, 41, 111, 5, 91, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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