Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 201405ef2835d1f5ad661d2c7e96aa952c465f20ec67312d6aefeb85b1a77066

Tx prefix hash: 6ed2c8a7cb1ce86cfed4414b91a79e4151bd36c4204cf22505d1a8063aef0a32
Tx public key: 7eb2a6918c4e9c97dce92dd0e8703c805e5da719ffa4bbbf029b8bf823412f15
Timestamp: 1715719384 Timestamp [UCT]: 2024-05-14 20:43:04 Age [y:d:h:m:s]: 00:224:12:23:51
Block: 1022066 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160710 RingCT/type: yes/0
Extra: 017eb2a6918c4e9c97dce92dd0e8703c805e5da719ffa4bbbf029b8bf823412f15021100000001c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04dc9f1eb1e1047fcfa3b45d518035fd8a3442e92b9eedbc1d4d71f42beb794d 0.600000000000 1486563 of 15

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": 1022076, "vin": [ { "gen": { "height": 1022066 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04dc9f1eb1e1047fcfa3b45d518035fd8a3442e92b9eedbc1d4d71f42beb794d" } } ], "extra": [ 1, 126, 178, 166, 145, 140, 78, 156, 151, 220, 233, 45, 208, 232, 112, 60, 128, 94, 93, 167, 25, 255, 164, 187, 191, 2, 155, 139, 248, 35, 65, 47, 21, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 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