Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04f4ee9a1529e9e03277ef5899da74cf2486bee02a62ce9a5c7be13313d2d406

Tx prefix hash: 81b44053597104303f8781d440c91bf664b03b3f2ee8b24c49810771e7b0d159
Tx public key: 8c8de0a833c916d0d4b59710868b042638c649439b4c69c33253498b683b0016
Timestamp: 1579199213 Timestamp [UCT]: 2020-01-16 18:26:53 Age [y:d:h:m:s]: 04:294:10:37:01
Block: 47004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1099857 RingCT/type: yes/0
Extra: 018c8de0a833c916d0d4b59710868b042638c649439b4c69c33253498b683b0016021100000001b221b3d1000000000000000000

1 output(s) for total of 428.809677352000 dcy

stealth address amount amount idx
00: bf9dc3f480c3f905b1de6dac5498eec40935810203aedf67d731dd2e9226b9f9 428.809677352000 86757 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": 47014, "vin": [ { "gen": { "height": 47004 } } ], "vout": [ { "amount": 428809677352, "target": { "key": "bf9dc3f480c3f905b1de6dac5498eec40935810203aedf67d731dd2e9226b9f9" } } ], "extra": [ 1, 140, 141, 224, 168, 51, 201, 22, 208, 212, 181, 151, 16, 134, 139, 4, 38, 56, 198, 73, 67, 155, 76, 105, 195, 50, 83, 73, 139, 104, 59, 0, 22, 2, 17, 0, 0, 0, 1, 178, 33, 179, 209, 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