Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fae84be98c7486b426c1413625db00942038a18e3c084b14aaa00b9c760ac97

Tx prefix hash: ce6ef395d5397425cd28761b3d5550f9a4e3d4a0308a903aac780042345e6732
Tx public key: f85c1d034989425df0884e5027307c9620816e4a0a06fd9fb3e6a90b485a692f
Timestamp: 1649001681 Timestamp [UCT]: 2022-04-03 16:01:21 Age [y:d:h:m:s]: 02:345:15:13:15
Block: 472394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 766564 RingCT/type: yes/0
Extra: 01f85c1d034989425df0884e5027307c9620816e4a0a06fd9fb3e6a90b485a692f02110000000a2e6b1fd5000000000000000000

1 output(s) for total of 16.705642505000 dcy

stealth address amount amount idx
00: 5595f339152cfce687bfc1d48e2a9e98fde62e43872e9f0a716932019859cea8 16.705642505000 891938 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": 472404, "vin": [ { "gen": { "height": 472394 } } ], "vout": [ { "amount": 16705642505, "target": { "key": "5595f339152cfce687bfc1d48e2a9e98fde62e43872e9f0a716932019859cea8" } } ], "extra": [ 1, 248, 92, 29, 3, 73, 137, 66, 93, 240, 136, 78, 80, 39, 48, 124, 150, 32, 129, 110, 74, 10, 6, 253, 159, 179, 230, 169, 11, 72, 90, 105, 47, 2, 17, 0, 0, 0, 10, 46, 107, 31, 213, 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