Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe4d7e82fc0f5f06e6e01cb64359d873286740d777550cbee7355cd9b55a5b84

Tx prefix hash: 7dbebfb9dfcae17a2644ef2d4d26091bd4dc2984a95330e9f48d1bcbc2c5eb6e
Tx public key: 44d371154ff6074fd5a0fb1b080bfb79f314f7a8641ae8f8aa831e74ca23393b
Timestamp: 1576273261 Timestamp [UCT]: 2019-12-13 21:41:01 Age [y:d:h:m:s]: 05:164:19:05:17
Block: 26429 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1264320 RingCT/type: yes/0
Extra: 0144d371154ff6074fd5a0fb1b080bfb79f314f7a8641ae8f8aa831e74ca23393b0211000000038a2ee0d9000000000000000000

1 output(s) for total of 501.693086076000 dcy

stealth address amount amount idx
00: 879567f9a431e338fddb79f4d42d87bc89f08b0f144ddc1e6ac6087f3e269a2c 501.693086076000 43804 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": 26439, "vin": [ { "gen": { "height": 26429 } } ], "vout": [ { "amount": 501693086076, "target": { "key": "879567f9a431e338fddb79f4d42d87bc89f08b0f144ddc1e6ac6087f3e269a2c" } } ], "extra": [ 1, 68, 211, 113, 21, 79, 246, 7, 79, 213, 160, 251, 27, 8, 11, 251, 121, 243, 20, 247, 168, 100, 26, 232, 248, 170, 131, 30, 116, 202, 35, 57, 59, 2, 17, 0, 0, 0, 3, 138, 46, 224, 217, 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