Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 705a72434cbed2aa72a5b80480690888ee52e25ae40b15741525905db401b429

Tx prefix hash: 448da25bf8ec39bd65ecc2e9d651600ee01d10a0e3c04f56d30265b09e35d649
Tx public key: 2a02094319f954998ac521179c1b84f59725816452903b43aeaf505cb0d9b833
Timestamp: 1696126397 Timestamp [UCT]: 2023-10-01 02:13:17 Age [y:d:h:m:s]: 01:111:19:50:07
Block: 859837 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341154 RingCT/type: yes/0
Extra: 012a02094319f954998ac521179c1b84f59725816452903b43aeaf505cb0d9b833021100000009faf35c9c000000000000000000

1 output(s) for total of 0.868966684000 dcy

stealth address amount amount idx
00: d7c0fbd04d53f05c4e43e75a4b53c8066b87cb52d5715f2ff3e7d53f3cce4dcb 0.868966684000 1314085 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": 859847, "vin": [ { "gen": { "height": 859837 } } ], "vout": [ { "amount": 868966684, "target": { "key": "d7c0fbd04d53f05c4e43e75a4b53c8066b87cb52d5715f2ff3e7d53f3cce4dcb" } } ], "extra": [ 1, 42, 2, 9, 67, 25, 249, 84, 153, 138, 197, 33, 23, 156, 27, 132, 245, 151, 37, 129, 100, 82, 144, 59, 67, 174, 175, 80, 92, 176, 217, 184, 51, 2, 17, 0, 0, 0, 9, 250, 243, 92, 156, 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