Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40e088acb5fcec36214f0fda4111bc7ed6a6895f370d60f54f45134adc796a25

Tx prefix hash: 08387d6044b35a90f30dfce0fc5e61a904b0fb634857ea3158c203ab84578af9
Tx public key: 98c38c194d9d6d90e9ca91a251ecf5ec84bb442bc4b62fbff11d267b0f797ad1
Timestamp: 1634249308 Timestamp [UCT]: 2021-10-14 22:08:28 Age [y:d:h:m:s]: 03:211:19:34:51
Block: 353144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 929044 RingCT/type: yes/0
Extra: 0198c38c194d9d6d90e9ca91a251ecf5ec84bb442bc4b62fbff11d267b0f797ad10211000000655410958b000000000000000000

1 output(s) for total of 41.484680526000 dcy

stealth address amount amount idx
00: 323afb8a375d2bacab9bcde6a9fb4fcc2e7e8ddf2efe6ee73f06529ace9c8ac3 41.484680526000 721686 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": 353154, "vin": [ { "gen": { "height": 353144 } } ], "vout": [ { "amount": 41484680526, "target": { "key": "323afb8a375d2bacab9bcde6a9fb4fcc2e7e8ddf2efe6ee73f06529ace9c8ac3" } } ], "extra": [ 1, 152, 195, 140, 25, 77, 157, 109, 144, 233, 202, 145, 162, 81, 236, 245, 236, 132, 187, 68, 43, 196, 182, 47, 191, 241, 29, 38, 123, 15, 121, 122, 209, 2, 17, 0, 0, 0, 101, 84, 16, 149, 139, 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