Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bea1ba984231300558ecced4e0d8bc6bd4deec138f9df77f78349f156b3fa564

Tx prefix hash: d1e3145bcb4b80a663acf1411e952da0800dcf04f1a9016af1cdf286eb1ba162
Tx public key: 0ce1d5b050f7ac8fd3d2aa3a16a90759dd9a7c79c21044161af2eab0792c13e9
Timestamp: 1621170501 Timestamp [UCT]: 2021-05-16 13:08:21 Age [y:d:h:m:s]: 03:267:22:09:00
Block: 261606 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 952438 RingCT/type: yes/0
Extra: 010ce1d5b050f7ac8fd3d2aa3a16a90759dd9a7c79c21044161af2eab0792c13e902110000000d85d8f8f2000000000000000000

1 output(s) for total of 83.404843200000 dcy

stealth address amount amount idx
00: 34251e2c3fd7ec2709d6e9ae8924c7922df8e8d2897cea24b5ec42a0f365f026 83.404843200000 550607 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": 261616, "vin": [ { "gen": { "height": 261606 } } ], "vout": [ { "amount": 83404843200, "target": { "key": "34251e2c3fd7ec2709d6e9ae8924c7922df8e8d2897cea24b5ec42a0f365f026" } } ], "extra": [ 1, 12, 225, 213, 176, 80, 247, 172, 143, 211, 210, 170, 58, 22, 169, 7, 89, 221, 154, 124, 121, 194, 16, 68, 22, 26, 242, 234, 176, 121, 44, 19, 233, 2, 17, 0, 0, 0, 13, 133, 216, 248, 242, 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